5 Upgrading MyID

This chapter contains important information on upgrading your MyID system. The upgrade procedure you must carry out depends on what version of MyID you are upgrading.

5.1 Before you upgrade

Note: Before you upgrade your MyID system to the current version of MyID, contact Intercede customer support quoting reference SUP-300 for advice on upgrading your particular configuration; this is essential if your system contains any customizations, or if you are upgrading from a system earlier than version 8.0.

Check section 3, Hardware and software requirements to make sure that your system supports the latest version of MyID, and section 4, Preparing your system to make sure that your system has been configured correctly. You can use the System Interrogation Tool to confirm that your system meets the requirements for the current version of MyID – see the System Interrogation Utility guide for details.

Make sure that your client workstations are correctly configured; see section 3.3, Client workstation. For example, make sure that the MyID website has not been added to the list of compatibility view sites on any of your client PCs.

MyID 10.7 introduced the requirement to have the SQL Server Full Text Search option installed on your database server, and MyID 11.0 introduced the requirement to have the Microsoft OLE DB Driver 18.1 for SQL Server (MSOLEDBSQL) installed – see section 4.5, Setting up the database for details.

MyID 10.7 also introduced the web service user account. If you are upgrading a MyID 10.6 or earlier system, you must create this user before you run the installation program; see section 4.1, Setting up user accounts for details.

MyID 11.0 introduced the requirement for the MyID COM+ user account, the IIS user account, and the web service user account to have Log on as a service rights – if you are upgrading, you must make sure that your accounts have the correct permissions; see section 4.1, Setting up user accounts for details.

Make sure that you complete any outstanding activation jobs before upgrading your system – if you request a card, upgrade MyID, then attempt to activate the card, you may experience problems due to the different requirements for activation between versions of MyID. For more information contact customer support quoting reference SUP-182.

5.1.1 Upgrading systems with custom configuration updates

If you have received an update from Intercede for your pre-MyID 11.4 system that applies custom configurations – for example CONFIG-9999.1.0 – you must contact customer support quoting reference SUP-318 to receive an updated version of this configuration update.

5.1.2 Upgrading systems with custom LDAP mappings

If the MyID system you are upgrading has custom LDAP mappings, before you upgrade you must set a configuration option to prevent the installation program from overwriting your existing settings.

To retain your custom LDAP mappings while upgrading:

  1. From the Configuration category, select Operation Settings.

  2. On the LDAP tab, select the following:

    • Custom LDAP mappings – set to Yes.
  3. Click Save changes.

5.1.3 Upgrading systems with a web server outside the domain

If your system has been configured to use a web server outside the domain used for the rest of the MyID system, the custom configuration on the MyID application components presents some complications when upgrading. If your system meets this description, you are recommended to contact customer support quoting reference SUP-242.

5.1.4 Upgrading renewal jobs

If you are upgrading from a MyID 10.4 or earlier system, you are recommended to complete all outstanding renewal jobs before upgrading. If this is not possible, you can use the provided database scripts to cancel the existing jobs and then regenerate them.

The database scripts are provided in the MyID release in the following folder:

\Support Tools\Upgrade\Database Scripts\

To upgrade your renewal jobs:

  1. Before upgrading, run the following script against the MyID database:

    db_CountPendingCertRenewals.sql

    This script informs you how many pending renewal jobs are in the MyID database.

  2. Carry out the MyID upgrade.

  3. After upgrading, run the following script against the MyID database:

    db_RegeneratecCertRenewalJobs.sql

    This script cancels the renewal jobs and regenerates them so that they can be processed.

5.1.5 Upgrading card issuance jobs

If you are upgrading from a MyID 8.0 or earlier system, you are recommended to complete all outstanding issuance jobs before upgrading.

You may find that the Collect Card workflow has the following issues with jobs that were created before you carried out the upgrade:

You can use the provided database script to upgrade these issuance jobs to the latest format.

The database script is provided in the MyID release in the following folder:

\Support Tools\Upgrade\Database Scripts\

To upgrade your issuance jobs:

  1. After upgrading MyID, run the following script against the MyID database:

    db_MigrateV8IssueCardJobs.sql

    This script upgrades the issuance jobs so that you can collect them.

5.1.6 Upgrading systems with customized configuration files

If you have made any changes to configuration files, such as the myid.config file for the various MyID web services, you must back up these files before you start the upgrade process, and merge in the changes once you have completed the new installation.

5.1.7 Upgrading systems with multiple databases

Your MyID system may have multiple databases; for example, a separate audit database, a separate audit archive database, or a binary objects database. You configure MyID to point to the appropriate database by configuring its .udl files; you are recommended to back up the MyID .udl files in the Windows SysWOW64 folder before you upgrade MyID.